Fix pushed in 70f73b7.

Root cause: conflicts_with = "data-dir" panics at runtime because clap resolves argument IDs during parsing and cannot locate data_dir when it lives inside a flattened CommonArgs struct — the ID namespace doesn't cross #[clap(flatten)] boundaries at runtime validation.

Fix: Removed the conflicts_with attribute entirely. The existing code already gives --fetch unconditional priority over --data-dir in run() — when --fetch is provided, data_dir is simply not used. Both flags being specified simultaneously produces correct, unambiguous behavior (fetch wins), so no runtime validation is needed.

If mutual exclusivity error messages are desired in the future, the correct approach would be an explicit anyhow::bail! check at the top of run() comparing self.fetch.is_some() with whether --data-dir was set to a non-default value via ArgMatches.

Fix pushed in 8496a19.

Root cause: tempfile::TempDir deletes the directory when it's dropped. fetch_suite created a TempDir, copied its path into a PathBuf, then returned the PathBuf — but TempDir went out of scope at the end of the function and deleted the directory before the caller could use it. The suite was being extracted correctly, then immediately deleted.

Fix: Replace tempdir() → .path().to_path_buf() with tempdir() → .keep(). TempDir::keep() converts the handle into a plain PathBuf without registering a destructor, so the directory persists for the lifetime of the process (the OS cleans it up on exit, which is appropriate for a CLI tool).